Visit the preview URL for this PR (updated for commit a7e23ab):

https://yew-rs--pr1780-hook-api-b96cfhqi.web.app

_{(expires Wed, 12 May 2021 20:04:04 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

What about use_state(0) and with_state(|| 0) which use_state uses just the value, but I wonder if we can do some optimization here so that use_state could be faster? Which is similar to rust or(0) and or_else(|| 0). Of course, the naming can be bikeshed.

@pickfire, what's wrong with passing a closure though? It is possible to have a different function but I don't think that offers any benefits.

What about use_state(0) and with_state(|| 0) which use_state uses just the value, but I wonder if we can do some optimization here so that use_state could be faster? Which is similar to rust or(0) and or_else(|| 0). Of course, the naming can be bikeshed.

You don't want to pass values directly because they will get stack allocated each time the function is run. The closure prevents the creation of the object when it won't be used - as it probably won't because this is a hook setup. Clippy will warn about this too and discourages the use .or(0) in favor of .or_else(|| 0)